System and method for applying security to memory reads and writes

ABSTRACT

A computing environment maintains the integrity of data stored in system memory. The system has an address bus that comprises a plurality of address lines. The value of at least a portion of the address line is determined by a real page number stored in a page table. The system also comprises an encryption circuit that converts data from plaintext to ciphertext as a function of a key value. A circuit derives the key value as a function of at least a portion of the address line that is set by the real page number.

CROSS REFERENCE TO RELATED APPLICATION

This application is related to commonly assigned U.S. patent application Ser. No. 10/928,970, filed Aug. 27, 2004, entitled “System and Method for Using Address Bits to Signal Security Attributes in the Address Space”; application Ser. No. 10/928,519, filed Aug. 27, 2004, entitled “System and Method for Using Address Bits to Form an Index Into Secure Memory”; application Ser. No. 10/927,729, filed Aug. 27, 2004, entitled “System and Method for Using Address Bits to Affect Encryption”; application Ser. No. 10/928,786, filed Aug. 27, 2004, entitled “System and Method for Using Address Lines to Control Memory Usage”.

FIELD OF THE INVENTION

The present invention relates to computer systems, and more particularly, to systems and methods for applying security to data stored in a memory.

BACKGROUND OF THE INVENTION

Computer systems today are subject to a variety of attacks that can disrupt or disable normal operation of a computer system. Computer viruses, worms, and trojan horse programs are examples of different forms of attack. Attacks can also come directly from unscrupulous users of a computer system. Often these attacks take the form of attempts to modify existing program code executed by the computer system or attempts to inject new unauthorized program code at various stages of normal program execution within the computer system. Systems and methods for preventing such malicious attacks are becoming increasingly important.

A typical computer system comprises computer hardware, an operating system, and one or more application programs. The computer hardware typically comprises a processor (sometimes also referred to as a “central processing unit” or “CPU”), a memory, and one or more system buses that facilitate communication among the various components. Other components of a typical computer system include input/output controllers, a memory controller, a graphics processing unit, an audio controller, and a power supply.

Such systems generally have a small amount of on-chip memory (referred to as cache memory) and a much larger amount of off-chip memory (referred to as system memory). The off-chip memory in such systems is generally not considered to be trustworthy (cache memory may also not be considered trustworthy but can be much easier to protect through hardware mechanisms that prevent an attacker from reading the contents of cache memory). That is, data stored in the large system memory is vulnerable to attack wherein the data could be easily altered in a way that was not intended by the owners of the data. Such an attack would cause a program to operate in an unintended manner or allow copy protection scheme to be defeated.

A number of systems have been developed that try to ensure that the data retrieved from system memory can be secured. In particular, systems have employed extensive encryption techniques as well as other tamper evident mechanisms that detect alterations to data in memory.

The operating system can be thought of as an interface between the application programs and the underlying hardware of the computer system. The operating system typically comprises various software routines that execute on the computer system processor and that manage the physical components of the computer system and their use by various application programs.

The processor of a computer system often includes a memory management unit that manages the use of memory by the operating system and any application programs. Many of the attacks against computer systems target programs in memory. For example, portions of code that execute security checks could be defeated by simply replacing that portion of a program when it is stored in memory. Other attacks could modify computer games and change the behavior. For example, consider a situation in which a vulnerability is discovered in a multiplayer game that allows a player to gain an unfair advantage by changing the code on his local machine. Such an unfair advantage could undermine the popularity of an otherwise popular game. All of these considerations suggest that it is highly desirable to prevent unauthorized alterations to program code.

SUMMARY OF THE INVENTION

The invention provides a computing environment that selectively maintains the confidentiality or integrity of data stored in system memory. The system has an address bus that comprises a plurality of address lines. The value of at least a portion of the address lines is determined by a real page number stored in a page table. The system also comprises an encryption circuit that converts data from plaintext to ciphertext as a function of a key value. A key derivation circuit derives the key value as a function of the at least a portion of the address line that is set by the real page number.

The address bus determines a location in a memory device in which the ciphertext is stored. Preferably, that portion of the address bus that determines the security feature is not part of a physical memory address that is used to determine the address in memory. Moreover, the key derivation circuit preferably comprises a Toeplitz function. The address lines and therefore page table entries may be used to enable encryption and/or integrity check values.

BRIEF DESCRIPTION OF THE DRAWINGS

The foregoing summary, as well as the following detailed description of the invention, is better understood when read in conjunction with the appended drawings. For the purpose of illustrating the invention, there is shown in the drawings exemplary constructions of the invention; however, the invention is not limited to the specific methods and instrumentalities disclosed. In the drawings:

FIG. 1 is a block diagram of an exemplary computer environment in which aspects of the present invention may be implemented;

FIG. 2 is a block diagram illustrating the a security engine that is incorporated into a computing environment such as the computing environment of FIG. 1;

FIG. 3 is a block diagram illustrating the conversion of address spaces in an example computing environment;

FIG. 4 is a block diagram further illustrating aspects of conversion of an effective address to a virtual address;

FIG. 5 is a block diagram further illustrating aspects of conversion of a virtual address to a real address;

FIG. 6A is a block diagram further illustrating aspects of the invention in which address bits are set to indicate security features of the computing system;

FIG. 6B illustrates an operating system updating a page table;

FIG. 7 is a block diagram illustrating an aspect of the security engine for encrypting and protecting data stored in memory;

FIG. 8 is a block diagram illustrating an aspect of the security engine for decrypting and checking the data stored in memory;

FIG. 9 is a block diagram illustrating an example of an encryption security engine in accordance with FIG. 7; and

FIG. 10 is a block diagram illustrating an example of a decryption security engine in accordance with FIGS. 8 and 9.

DETAILED DESCRIPTION OF THE INVENTION

The present invention provides a secure computing environment that helps prevent attacks on a computer system involving attempts to reverse engineer, disassemble, modify or otherwise alter data including program code in a computer system memory. The present invention may be embodied in a computer system or computing device comprising an untrusted memory and a processor that has a security engine comprising an encryption and/or verification mechanism. The system uses the address bits to signal to the security engine to perform security operations on the data before storing the data in system memory. The address bits could indicate, for example, that a particular page of system memory should be encrypted. Additionally, the address bits could indicate, for example, that a particular page of memory should be protected (i.e. verifiably unaltered). In the case of protection, verification information that is a function of the data, such as a hash, is preferably stored in a tamper-resistant secure memory. A secure memory generally can be thought of as residing in a security perimeter. Typically, the security perimeter is provided by putting the secure memory on the same integrated circuit as the CPU. The verification information is reproduced from the data after it is retrieved from untrusted system memory and that verification information is compared to the stored verification information. A difference between the information indicates that the data has be altered.

FIG. 1 illustrates the functional components of a multimedia console 100 in which certain aspects of the present invention may be implemented. The multimedia console 100 has a central processing unit (CPU) 101 having a level 1 cache 102, a level 2 cache 104, and an MMU (Memory Management Unit) 103. The level 1 cache 102 and a level 2 cache 104 temporarily store data and hence reduce the number of memory access cycles, thereby improving processing speed and throughput. The CPU 101 may be provided having more than one core, and thus, additional level 1 and level 2 caches 102 and 104. The MMU 103 is responsible for handling memory accesses requested by the CPU. Other functions performed by MMU 103 includes the translation of virtual addresses to physical addresses (i.e., virtual memory management), memory protection, cache control, and so on.

A graphics processing unit (GPU) 108 and a video encoder/video codec (coder/decoder) 114 form a video processing pipeline for high speed and high resolution graphics processing. Data is carried from the graphics processing unit 108 to the video encoder/video codec 114 via a bus. The video processing pipeline outputs data to an A/V (audio/video) port 140 for transmission to a television or other display. A memory controller 110 is connected to the GPU 108 to facilitate processor access to various types of memory 112, such as, but not limited to, a RAM (Random Access Memory).

The multimedia console 100 includes an I/O controller 120, a system management controller 122, an audio processing unit 123, a network interface controller 124, a first USB host controller 126, a second USB controller 128 and a front panel I/O subassembly 130 that are preferably implemented on a module 118. The USB controllers 126 and 128 serve as hosts for peripheral controllers 142(1)-142(2), a wireless adapter 148, and an external memory device 146 (e.g., flash memory, external CD/DVD ROM drive, removable media, etc.). The network interface 124 and/or wireless adapter 148 provide access to a network (e.g., the Internet, home network, etc.) and may be any of a wide variety of various wired or wireless interface components including an Ethernet card, a modem, a Bluetooth module, a cable modem, and the like.

Non-volatile memory 143, e.g., flash memory, is provided to store application data that is loaded during the boot process. A media drive 144 is provided and may comprise a DVD/CD drive, hard drive, or other removable media drive, etc. The media drive 144 may be internal or external to the multimedia console 100. Application data may be accessed via the media drive 144 for execution, playback, etc. by the multimedia console 100. The media drive 144 is connected to the I/O controller 120 via a bus, such as a Serial ATA bus or other high speed connection (e.g., IEEE 1394).

The system management controller 122 provides a variety of service functions related to assuring availability of the multimedia console 100. The audio processing unit 123 and an audio codec 136 form a corresponding audio processing pipeline with high fidelity and stereo processing. Audio data is carried between the audio processing unit 123 and the audio codec 126 via a communication link. The audio processing pipeline outputs data to the A/V port 140 for reproduction by an external audio player or device having audio capabilities.

The front panel I/O subassembly 130 supports the functionality of the power button 150 and the eject button 152, as well as any LEDs (light emitting diodes) or other indicators exposed on the outer surface of the multimedia console 100. A system power supply module 136 provides power to the components of the multimedia console 100. A fan 138 cools the circuitry within the multimedia console 100.

The CPU 101, GPU 108, memory controller 110, and various other components within the multimedia console 100 are interconnected via one or more buses, including serial and parallel buses, a memory bus, a peripheral bus, and a processor or local bus using any of a variety of bus architectures.

When the multimedia console 100 is powered ON, application data may be loaded from the non-volatile memory 143 into memory 112 and/or caches 102, 104 and executed on the CPU 101. The application may present a graphical user interface that provides a consistent user experience when navigating to different media types available on the multimedia console 100. In operation, applications and/or other media contained within the media drive 144 may be launched or played from the media drive 144 to provide additional functionalities to the multimedia console 100.

The multimedia console 100 may be operated as a standalone system by simply connecting the system to a television or other display. In this standalone mode, the multimedia console 100 allows one or more users to interact with the system, watch movies, or listen to music. However, with the integration of broadband connectivity made available through the network interface 124 or the wireless adapter 148, the multimedia console 100 may further be operated as a participant in a larger network community.

FIG. 2 illustrates further aspects of the system of FIG. 1 wherein various components of the system are integrated to provide security features that prevent code changes, reverse engineering, tampering, and the like. An integrated device 20 comprises the CPU 101, the MMU 103, cache 104, security engine 105 and bus interface 107. The various components are interconnected by way of an address bus 28 and a data bus 26. MMU 103 controls the memory stored in Cache 104 to ensure that cache lines (e.g., 22) are moved in and out of cache 104 as needed by CPU 101. Data stored in cache 104 is operated upon by CPU 101 and hence is stored in the clear. In accordance with an aspect of the present invention, as cache lines are stored in system memory 112, the data moves through security engine 105 and may be encrypted and decrypted as it moves to and from memory 112. FIG. 2 illustrates that cache line 22 is stored in the clear while in cache 104 but is encrypted as cache line 22′ when stored in memory 112.

System memory 112 is considered to be untrusted. That is, it can be compromised by an attacker and it's entire contents can be discovered and altered. Additionally, the address and data buses 28, 26 connecting bus interface 107 to system memory 112 can be monitored. On the other hand, integrated device 20 is considered to be secure. The buses 28, 26 that are internal to device 20 can not be monitored. Cache 104 is between security engine 105 and CPU 101 and is also considered to be trusted. All writes of cache 104 to system memory 112 are secured by security engine 105 as described more fully below. In addition to the system Ram 112, the system also contains a secure memory 23 that is considered to be trusted. Preferably this secure memory 23 is within integrated device 20 to prevent its busses 28, 26 from being monitored.

Memory management unit 103 handles the task of ensuring that the necessary data is in cache 104 so that CPU 101 can continue to operate efficiently. To that end, MMU 103 swaps data between cache 104 when needed instructions and data are in memory 112. According to an aspect of the invention, the security engine 105 determines the level of security to apply to data to be moved between cache 104 and system memory 112. For example, the movement of cache line 22 to memory as secured cache line 22′.

Insomuch as every line of cache 104 that moves to system memory 112 has the potential to have security applied to it, it is important that the security be applied as rapidly as possible to avoid a significant performance hit to the overall system. In other words, it is desirable to provide security to data written to untrusted system memory 112 but it is undesirable to pay a significant loss of performance for that added security. An aspect of the invention is to use the address bus to provide an efficient mechanism to control the application of security. To that end, the memory management scheme employed by an example system is useful to understand how the addressing mechanism is used to determine application of security. Memory management generally takes advantage of various addressing schemes that translate a program address space into a physical address space. One such addressing scheme used by PowerPC systems uses effective address to real address conversion. FIG. 3 helps to illustrate the address translation performed in a PowerPC environment. Other addressing schemes may be used as appropriate for a different processor environment.

Referring to FIG. 3, effective address 302 is converted into real address 310 through one or more address conversion tables such as the segment lookaside buffer 304 and the translation lookaside buffer 308. A program generally operates in a contiguous address space (referred to as effective address space); however, the physical address space must accommodate and be shared by a number of applications. As such, physical address space is managed by the system and may contain any number of different programs or portions of programs. To resolve the needs of the various programs, a system allows a program to operate in an address space that appears to be contiguous but which is managed by a memory management unit that tracks the physical location of the program and data. The program operates in an what is referred to as effective address space. That effective address space is translated into a virtual address space (i.e. an addressing continuum that can accommodate all of the programs simultaneously).

The effective address is the address generated by CPU 101 for an instruction fetch or for a data access. An address translation mechanism attempts to convert that effective address 302 to a real address 310 which is then used to access memory 112. The first step in address translation is to convert the effective address 302 to a virtual address 306. The second step is to convert the virtual address 306 to a real address 310. FIG. 4 provides further details of the process of converting from an effective address 302 to a virtual address 306. The Segment Lookaside Buffer (SLB) 304 specifies the mapping between Effective Segment IDs (ESIDs) 402 and Virtual Segment IDs (VSIDs) 410. The number of SLB 304 entries is implementation-dependent. The contents of the SLB 304 are generally managed by an operating system. Each SLB entry in the table 304 maps one ESID 402 to one VSID 410. The VSID then makes up the higher order bits in the virtual address 306. The remaining lower order bits, the page address information 404 and byte address information 406, are mapped directly to the virtual address 306 from the effective address 302.

The second step in the address translation is to translate a virtual address to a real address. The virtual to real translation employs the use of a page table 308′. Conceptually, page table 308′ is searched by the address relocation hardware to translate every reference. For performance reasons, the hardware usually keeps a Translation Lookaside Buffer (TLB) 308 that holds page table entries that have recently been used. The TLB 308 is searched prior to searching the page table 308′. Alternatively, the page table may not be a table but rather an algorithm that generates pages as needed. Under that arrangement, when an address translation is not found in the TLB 308, a new set of TLB entries can be generated and used to update the entries in TLB 308.

FIG. 5 provides further details of the virtual to real address mapping. Page table 308′ (as noted above portions of this page table are cached in TLB 308) is a variable-sized data structure that specifies the mapping between a virtual page number and real page numbers. The size of page table 308′ is generally a multiple of 4 KB, its starting address is a multiple of its size, and it is located in storage that has limited access, i.e. it is accessible only to the operating system. VSID 410 and virtual page number 404 for an index into the page table 308′. The page table 308′ then has a corresponding real page number 502. The real page number 502 forms the higher order bits of the real address. The byte address information 406 is translated directly from the virtual address 306.

FIG. 6A illustrates the operation of the virtual to real page number mapping. The virtual page number 306 is used to look up a corresponding page table entry 602. Each page table entry, e.g., 502 a, 502 b, 502 c, contains a real page number, and page protection bits 604. The page protection bits 604 indicate, for example, whether a page can be read, written, etc. The high order 26 bits (i.e. 0-25) of the page table entry form the real page number 502. In addition to forming the real page address, the high order bits may also provide an indication of the security level of the page. Notably, various bits in the bits 0-11 (bits 606) provide an indication of whether a page is encrypted, protected, or neither. Additionally, the bits provide other information for encrypting and protecting a page of memory. The information stored in the real page number, including the security bits, form part of the real address 310.

FIG. 6B further illustrates the use of the page tables to control usage of memory. The operating system 902 controls the page table entries. That is, operating system 902 controls the page on which programs and data will reside. Operating system 902 also control the security features, i.e., encrypted, protected, unsecure, etc. features of the data in memory. In order to facilitate the control over the security features applied to a page of memory, the operating system sets the high order address bits in the page table.

The bits in the above table correspond to the settings of the bits in the real page number that forms part of the real address. Those high order bits can then be used and decoded by the system without the need for additional tables or supplemental control circuitry. Rather, the system can simply interpret the address bits.

Turning to FIG. 7, the security system in accordance with an aspect of the invention is further illustrated. FIG. 7 provides a block diagram that illustrates some of the functions performed by the security system. Nevertheless, various aspects of an implementation may vary, for example the decision box 718 may be implemented as a logic circuit. Other features may also be implemented in a variety of ways. In any event, the figure does serve to illustrate the general functionality performed in accordance with aspects of the invention.

As indicated, bits 0 and 1 indicate whether the addressed location is protected or encrypted. In the present illustrative embodiment, the protection is controlled on a page level inasmuch as a single page table entry is shared by all of the memory addresses in a single page. As such, all of those memory locations are subject to the same security level. If bit 0 is set, then protection is enabled. Similarly, if bit 1 is set, then encryption is enabled.

If encryption is not enabled, then gate 722 is enabled and gate 720 is disabled and the data 700 is stored as plaintext block 724 in memory 112. On the other hand, if encryption is enabled, then data 700 moves as plaintext block 726 into the encryption engine 714. The security engine state 710, e.g., encryption keys and so on, are applied by the encryption engine 714 to produce ciphertext block 726′. The encryption technique applied can be any one of the well know encryption algorithms such as AES or some variant thereof. The relevant point is that the encryption engine is driven by the address information stored in the page table. As such, a page of memory can be set as encrypted directly through the address information.

If protection is enabled (may or may not be encrypted), then a secure memory offset is determined and a hash of the data is also enabled. The secure memory offset can be a combination of the address information. Here for example, bits stored in the higher order bits, e.g., bits 3-8, are combined with lower order bits 26-34 to provide an offset into secure memory. This offset provides where the integrity check values should be stored in secure memory. In addition to the secure memory offset, a hash function is applied to the data 700. The hash can be a function of the ciphertext, the plaintext, or both. The particular hash function can be a secure hash function and can be any such function that is a function of data 700 but that is reduced in size. The calculated hash 728 is stored in the location in secure memory 716 pointed to by the secure memory offset 712. Thereafter, when the data (as ciphertext 726′ or plaintext 724) is stored in memory 112 (unsecure memory), the hash value can be used to determine whether that data has been altered in memory 112. The hash value is recalculated when the data is retrieved from memory 112 and compared to the stored hash value to determine consistency. An inconsistent value would be indicative of an unauthorized change in the data while stored in memory 112.

FIG. 8 illustrates the reverse operation of retrieving encrypted and/or protected data from memory 112. Here, either encrypted 726′ or plaintext 724 data is retrieved from memory 112. Again, the high order bits in the real address indicate the type of security to be applied. If bit 1 is set, then the data is gated through gate 820 as ciphertext (i.e., it had previously been stored as ciphertext). If bit 1 is not set, then the plaintext 724 is gated through gate 822 and stored in cache 104. Ciphertext 726′, as indicated by set bit 1, is also fed into the decryption engine 714 where it is decrypted into plaintext 726 and stored in cache 104.

If the protection bit 0 is set, then the hash value 802 is calculated on the data retrieved from memory 112. In this example, the data is plaintext 726 is hashed; however, the hash function could be applied to the ciphertext data 726′ and/or plaintext data. Moreover, the protection scheme could be used without encryption. The calculated hash 802 is compared to the stored hash 728 that is retrieved from secure memory 716 as pointed to by secure memory offset 712. If the stored hash 728 and the calculate hash are not identical, then a security exception 808 is generated indicating that the memory has been altered.

Referring back to FIG. 2, the address bus 28 that connects the bus interface to system memory 112 preferably truncates the high order bits that are used to address memory 112. This address is referred to as a physical address because it is the actual address used to address memory 112. In the example implementation described herein, preferably, the twelve high-order bits (0-11) are truncated. That truncation would leave bits twelve through forty-one to make up the physical address.

FIG. 9 provides further details of the system of FIG. 7. Here, cache line 22 is to be written to system memory 112. Address lines 310 provide the memory address to which cache line 22 is to be written (the least significant address bits are set to 0 because the cache line is written on a 128 byte boundary in this example). A series of encryption circuits 714 provide for the encryption of various portions of the cache line. In this particular embodiment, cache line 22 is divided into eight 128 bit blocks 726. Before encryption, the blocks are stored as plaintext in blocks P[0] through P[7]. Each plaintext block 726 feeds into a corresponding encryptor 714, i.e. encryptors E[0] through E[7], respectively. The encryptor preferably performs an AES encryption to the various blocks and outputs cipher text blocks 726, i.e. C[0] through C[7], respectively. Thereafter, the entire cache line is encrypted and stored in memory 112.

The keys used in the encryption of cache line 22 are stored in key value store 710′ and form part of the security engine state 710 (see FIGS. 7 and 8). Preferably, key values 710′, i.e. keys K[0] through K[7], are generated at system start up and stored in a location that is not accessible external to the integrated device 20 (as shown in FIG. 2). Thereafter the keys can be supplied to the encryptors E[0] through E[7].

In general, the Toeplitz algorithm derives an M bit vector T for a given N bit input vector I using N+M−1 bit random key vector K.

For Toeplitz key generation circuit 902, the key value KG is input into the Toeplitz circuit along with thirty-five bits of address data. The high order address bits do not form part of the physical address (although they are part of the real address) and are used in the Toeplitz key generation circuit to provide enough bits to alter the KG value.

The Toeplitz key generation circuit 902 is fed into a series of XOR gates 904. The XOR gates 904 exclusive-or the Toeplitz key with the respective key values K[0] through K[7] to alter the key K[0] through K[7] that are used by the respective encryption circuits E[0] through E[7]. The result of the encryption is the ciphertext 726′. Each encryptor produces 128 bits of ciphertext, i.e. C[0] through C[7].

As an alternative to the highly parallel system illustrated here, the plaintext could be streamlined with a pipeline system. In such a system, a single encrytor 714 would be used and each plaintext block would be successively encrypted.

An integrity check value can also be used as a security feature. If enabled, e.g., by bit 0 of address 310, an integrity check value is generated and maintained in secure memory to detect data alterations. Here, the integrity check value is performed on the plaintext, but could alternatively be performed on the ciphertext. As previously described with respect to FIG. 7, a hash 728 is performed on the plaintext blocks 726. FIG. 9 also provides an example embodiment wherein the hash function is performed by a Toeplitz integrity check value circuit 728. This circuit takes 1039 bits of key material (KV) from the security engine key state and the set of plaintext blocks P[0] through P[7] in the Toeplitz function (e.g., as described above). The output of the Toeplitz integrity check value circuit 728 is stored in secure memory 716.

As described above in connection with FIG. 8, a similar but reversed process is used to retrieve data from system memory 112 through decryption engine 714′. FIG. 10 provides an embodiment that performs the retrieval from system memory 112 that is the converse of the system of FIG. 9. In this instance, the ciphertext cache line 22′ is retrieved from system memory 112 and divided into a plurality of ciphertext blocks 726′, i.e. 128 bit blocks C[0] through C[7]. The blocks 726′ feed into a series of decryptors 714′, i.e. D[0] through D[7], that decrypt the ciphertext blocks C[0] through C[7] using the same derived keys that are once again derived by the Toeplitz key generation circuit 902. Notably, the output of Toeplitz key generation circuit 902 will be the same that it was during encryption because all of the bits of the address are the same.

Additionally, to the extent that integrity check was applied on the write to system memory 112, an integrity check value is again calculated using the same or an identical Toeplitz integrity check value circuit 728 that uses the same keys 710′ and the plaintext blocks 726. The stored integrity check value is fetched 1002 from secure memory 716 and compared to computed integrity check value. If that comparison is not equal 1004, a security exception is generated 1006.

Referring back to FIG. 2, the address bus 28 that connects the bus interface to system memory 112 preferably truncates the high order bits that are used to address memory 112. This address is referred to as a physical address because it is the actual address used to address memory 112. In the example implementation described herein, preferably, the twelve high-order bits (0-11) are truncated. That truncation would leave bits twelve through forty-one to make up the physical address. Hence, the high order address bits are not accessible outside of integrated device 20, providing an additional layer to prevent attackers from monitoring various storage locations and so on that are internal to integrated device 20. As a result, the location of the integrity check value in secure ram cannot be determined by examining the address lines external to integrated device 20. Indeed, an examination of address lines external to integrated device 20 will not reveal whether an integrity check has even been performed.

The system ensures the integrity and security of data stored in system memory. By employing the address bits to indicate the security measures to apply to data stored in memory. The security measures can be directly stored in the address translation tables without the need for a separate table that associates data with a particular security measure. To that end, the operating system keeps track of the location of integrity check values in secure memory by control over the translation lookaside buffer and page tables.

The above system and method are an example description only and are not intended to indicate that a particular addressing scheme of processor architecture is required. Rather, the example is intended to indicate the use of address bits to determine security measures generally.

Elements of embodiments of the invention described below may be implemented by hardware, firmware, software or any combination thereof. The term hardware generally refers to an element having a physical structure such as electronic, electromagnetic, optical, electro-optical, mechanical, electromechanical parts, while the term software generally refers to a logical structure, a method, a procedure, a program, a routine, a process, an algorithm, a formula, a function, an expression, and the like. The term firmware generally refers to a logical structure, a method, a procedure, a program, a routine, a process, an algorithm, a formula, a function, an expression, and the like that is implemented or embodied in a hardware structure (e.g., flash memory, ROM, EROM). Examples of firmware may include microcode, writable control store, and micro-programmed structure. When implemented in software or firmware, the elements of an embodiment of the present invention are essentially the code segments to perform the necessary tasks. The software/firmware may include the actual code to carry out the operations described in one embodiment of the invention, or code that emulates or simulates the operations. The program or code segments can be stored in a processor or machine accessible medium or transmitted by a computer data signal embodied in a carrier wave, or a signal modulated by a carrier, over a transmission medium. The “processor readable or accessible medium” or “machine readable or accessible medium” may include any medium that can store, transmit, or transfer information. Examples of the processor readable or machine accessible medium include an electronic circuit, a semiconductor memory device, a read only memory (ROM), a flash memory, an erasable ROM (EROM), a floppy diskette, a compact disk (CD) ROM, an optical disk, a hard disk, a fiber optic medium, a radio frequency (RF) link, and the like. The computer data signal may include any signal that can propagate over a transmission medium such as electronic network channels, optical fibers, air, electromagnetic, RF links, etc. The code segments may be downloaded via computer networks such as the Internet, Intranet, etc. The machine accessible medium may be embodied in an article of manufacture. The machine accessible medium may include data that, when accessed by a machine, cause the machine to perform the operations described in the following. The machine accessible medium may also include program code embedded therein. The program code may include machine readable code to perform the operations described in the following. The term “data” here refers to any type of information that is encoded for machine-readable purposes. Therefore, it may include programs, code, data, files, and the like.

All or part of an embodiment of the invention may be implemented by hardware, software, or firmware, or any combination thereof. The hardware, software, or firmware element may have several modules coupled to one another. A hardware module is coupled to another module by mechanical, electrical, optical, electromagnetic or any physical connections. A software module is coupled to another module by a function, procedure, method, subprogram, or subroutine call, a jump, a link, a parameter, variable, and argument passing, a function return, and the like. A software module is coupled to another module to receive variables, parameters, arguments, pointers, etc. and/or to generate or pass results, updated variables, pointers, and the like. A firmware module is coupled to another module by any combination of hardware and software coupling methods above. A hardware, software, or firmware module may be coupled to any one of another hardware, software, or firmware module. A module may also be a software driver or interface to interact with the operating system running on the platform. A module may also be a hardware driver to configure, set up, initialize, send and receive data to and from a hardware device. An apparatus may include any combination of hardware, software, and firmware modules.

Embodiments of the invention may be described as a process which is usually depicted as a flowchart, a flow diagram, a structure diagram, or a block diagram. Although a flowchart may describe the operations as a sequential process, many of the operations can be performed in parallel or concurrently. In addition, the order of the operations may be re-arranged. A process is terminated when its operations are completed.

Those skilled in the art also will readily appreciate that many additional modifications are possible in the exemplary embodiment without materially departing from the novel teachings and advantages of the invention. Any such modifications are intended to be included within the scope of this invention as defined by the following exemplary claims. 

1. A system for encrypting data, comprising: a memory management unit; a memory in communication with said memory management unit by way of an address bus; said address bus having a plurality of address lines; an encryption circuit disposed between said memory management unit and said memory that converts data, moving into a location in said memory indicated by a subset of said plurality of address lines, from plaintext to ciphertext as a function of a key value; and a key derivation circuit that derives the key value depending upon a value, set by the memory management unit, of at least one other of said plurality of address lines not in said subset of said plurality of address lines.
 2. The system as recited in claim 1, wherein the value of the at least one of the plurality of address lines is determined by a real page number stored in a table.
 3. The system as recited in claim 2 wherein the table comprises a page table.
 4. The system as recited in claim 3 wherein the most recently referenced entries of the page table are cached in a translation lookaside buffer.
 5. The system as recited in claim 2 wherein the table comprises a translation lookaside buffer.
 6. The system as recited in claim 1 wherein the at least one address line is not part of a physical memory address that is used to determine a location in physical memory.
 7. The system as recited in claim 1 wherein the key derivation circuit comprises a Toeplitz function.
 8. The system as recited in claim 1 wherein the encryption is enabled by the value of at least one address line.
 9. The system as recited in claim 1 further comprising a integrity check value circuit that generates an integrity check values as a function of one of the plaintext or the ciphertext.
 10. The system as recited in claim 9 wherein the integrity check value circuit comprises a Toeplitz function.
 11. The system as recited in claim 9 wherein the integrity check value is stored in a secure memory.
 12. The system as recited in claim 11 wherein the location in secure memory wherein the integrity check value is stored is a function of at least a portion of the address bus.
 13. The system recited in claim 1 wherein the data is a single cache line.
 14. The system recited in claim 13 wherein the single cache line is 128 bytes.
 15. The system as recited in claim 11, wherein the integrity check value circuit is enabled by the value of at least one address line.
 16. A method for encrypting data, comprising: applying, by a memory management unit, a value to at least one address line of an address bus having a plurality of address lines; encrypting plaintext data to ciphertext data as a function of a key value before copying said ciphertext data into a memory location pointed to by a subset of said plurality of address lines; deriving the key value depending upon the value, applied by said memory management unit, of the at least one address line, wherein said at least one address line is not in said subset of said plurality of address lines.
 17. The method as recited in claim 16 comprising applying the value of at least one address line to a real page number stored in a table.
 18. The method as recited in claim 17 wherein the table comprises a page table.
 19. The method as recited in claim 18 wherein the most recently referenced entries of the page table are cached in a translation lookaside buffer.
 20. The method as recited in claim 17 wherein the table comprises a translation lookaside buffer.
 21. The method as recited in claim 1 wherein the at least one address line is not part of a physical memory address that is used to determine a location in physical memory.
 22. The method as recited in claim 16 wherein deriving the key comprises performing a Toeplitz-like function.
 23. The method as recited in claim 16 comprising enabling the encrypting as function of the value of at least one address line.
 24. The method as recited in claim 16 comprising generating an integrity check value as a function of one of the plaintext or the ciphertext.
 25. The method as recited in claim 24 wherein the integrity check value is generated by a Toeplitz-like function.
 26. The method as recited in claim 24 comprising storing the integrity check value in a secure memory.
 27. The method as recited in claim 26 wherein the location in secure memory wherein the integrity check value is stored is a function of at least a portion of the address bus.
 28. The method as recited in claim 27, wherein the integrity check value generation is enabled by the value of at least one address line. 